third-party-exp-api

Description: This API returns the transactionReferenceNo for the credit and debit amount coming in request.

Channel sends the request to mulesoft. Mulesoft will send the request to Loyalty sys api and get back the result.

A response is sent back to the channel immediately. If it fails due to any reason, a proper error is sent back to the API consuming channel to both REST using the error codes defined.

Mulesoft Request:

Headers:

Mandatory Headers: x-correlation-id, client_id, Authorization, x-channel-id, x-bank-id

Optional Headers: x-sub-channel-id, x-user-id, x-debug-flag, x-customer-id, client_secret

Paramaters:

URI Params: NA

Query Params: NA

Content-type: application/json

JSON Request:

{
    "creditAcctNo":  "4000215",
    "debitAmount": "200",
    "debitTheirRef": ""
}

Mulesoft Response:

Success Response: (200)

{
    "status": {
        "success": true,
        "code": "200",
        "arabicMessage": "تمت العملية بنجاح",
        "englishMessage": "The Operation has been Successfully Completed"
    },
    "transactionReferenceNo": "FT21025XXACC17CL"
}

Sample Error Response:

400 :

{
    "status": {
        "success": false,
        "code": "400",
        "reasonCode": "BadRequest",
        "arabicMessage": "لم يتم العثور على سجلات تطابق محددات البحث",
        "englishMessage": "No records were found",
        "backendError": "No records were found",
        "backendCode": "-100"
    }
}